home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-04
/
ov_all.zip
/
TI635.ASC
< prev
next >
Wrap
Text File
|
1991-09-11
|
8KB
|
265 lines
PRODUCT : ObjectVision NUMBER : 635
VERSION : 1.0
OS : WIN
DATE : September 11, 1991 PAGE : 1/4
TITLE : Simplifying your Windows system configuration.
Frequently UAE's (Unrecoverable Application Errors) and other
unexplainable problems in Windows are often due to software or
hardware conflicts/incomparability with other applications. In
the event of frequent UAE's and unusual problems, it is suggested
this be tested using the following procedure. It involves
eliminating all variables that can be causing problems and
repeating the steps that caused the UAE or other unusual problem.
It is intended as a test, not a permanent solution. If this
procedure succeeds you should restore your system and narrow down
the exact culprit by trial and error.
It is recommended that you have thoroughly read the readme.txt
files that accompany Windows 3.0 (README.TXT, 3270.TXT,
HEADER.TXT, PRINTERS.TXT, SYSINI.TXT, SYSINI2.TXT, SYSINI3.TXT,
WININI.TXT, and WININI2.TXT) and ObjectVision (README.TXT).
I will outline the eight steps involved in this testing process,
and give details later:
1.) Backup your system files.
2.) Reduce three different files to their bare minimum.
3.) Eliminate third party drivers from Windows SETUP.
4.) Close Windows, Reboot your system and restart Windows.
5.) Test your application.
6.) Restore your system.
7.) If necessary, using the process of elimination, narrow
down the culprit or culprits.
8.) Contact us (Borland) or the publisher of the offending
application.
Step 1.) Backup your system files.
Create a bootable floppy disk and copy your AUTOEXEC.BAT,
CONFIG.SYS, WIN.INI, and SYSTEM.INI files to this disk. In case
you have difficulty during this process, your system can be
completely restored by booting your system from this disk and
replacing these files.
Step 2.) Reduce three different files to their bare minimum.
This can be done by running a program, within Windows, called
SYSEDIT. From the file manager, select File|Run, and type
"SYSEDIT". This brings into the Windows Notepad the files
PRODUCT : ObjectVision NUMBER : 635
VERSION : 1.0
OS : WIN
DATE : September 11, 1991 PAGE : 2/4
TITLE : Simplifying your Windows system configuration.
AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, and SYSTEM.INI. Three of
these four files will be edited.
Select the AUTOEXEC.BAT file and use the DOS REM command to
exclude all (I emphasize all!) commands. Place in the
AUTOEXEC.BAT the commands PROMPT=$P$G, a PATH command, and, if
you are using one, the SET TEMP command. For example, if you
have Windows in a subdirectory C:\WINDOWS, DOS in C:\DOS, and a
swapfile subdirectory in C:\WINSWAP (if you do not use a
swapfile, ignore this), your AUTOEXEC.BAT file should look like
this:
PROMPT=$P$G
PATH=C:\WINDOWS;C:\DOS
SET TEMP=C:\WINSWAP
(Be absolutely sure this WINSWAP subdirectory exists!)
Select the CONFIG.SYS file and eliminate everything except
DEVICE=HIMEM.SYS, FILES=50 and BUFFERS=20. If you have a third
party hard disk driver, you must include this in the CONFIG.SYS
(if you are not sure about this, please check with the person who
low level formatted your drive). You will want to include the
command SHELL=C:\COMMAND.COM /p /e:2048. If Windows is in
C:\WINDOWS, and COMMAND.COM is in the ROOT directory, your
CONFIG.SYS should look like this:
SHELL=COMMAND.COM /p /e:2048
DEVICE=C:\WINDOWS\HIMEM.SYS
FILES=50
BUFFERS=20
You should have any hard disk drivers that are necessary (there
may be none), and should not have a disk cache (QEMM or
SMARTDRIVE) running at this time. If the meaning of any command
is unknown, leave it alone. It is recommended that you research
any unknown commands, eliminating them only if possible. If you
are on a network, run Windows without it if possible.
Select the WIN.INI file and find the commands "LOAD=" and "RUN=".
Delete everything on these lines, leaving "LOAD=" and "RUN=".
Leave everything else in this file alone.
PRODUCT : ObjectVision NUMBER : 635
VERSION : 1.0
OS : WIN
DATE : September 11, 1991 PAGE : 3/4
TITLE : Simplifying your Windows system configuration.
Now save these files and exit Windows (don't shell out in a DOS
Window).
Step 3.) Eliminate third party drivers from Windows SETUP.
This is relatively simple. Execute the SETUP.EXE program in the
Windows subdirectory (from DOS). Eliminate any OEM (Original
Equipment Manufacturer, ie. third party) drivers (especially
screen drivers). Replace these with the standard Microsoft
drivers. Please consult your Microsoft documentation, or the
Microsoft Tech. Support line for information about proper Setup
settings. (The Microsoft User's Guide section called Running
Setup from MS-DOS has information about running Setup from DOS.)
Step 4.) Be sure to close Windows, reboot your system and restart
Windows.
No explanation is needed here, however, this step is very
important. After rebooting (and BEFORE LOADING WINDOWS) execute
the CHKDSK and SET command to make sure everything is correct.
Execute the VER command and make sure the DOS version matches
your computer (ie PC DOS should only be used on true IBM's, not
clones).
Step 5.) Test your application.
Load the application in question. If you have specific steps to
reproduce the problem, follow them. If it is a problem that does
not occur regularly or predictably, you may have to leave this
configuration intact until you feel enough time has elapsed for
the problem to reoccur. If the problem does not reoccur, the
assumption is that there is some conflict with something that has
been eliminated from one of the three files, or it is an OEM
driver you removed in Setup.
Step 5.) Restore your system.
Restore the AUTOEXEC.BAT, CONFIG.SYS, SYSTEM.INI, and WIN.INI
files that were backed up in step 1.
Step 7.) If necessary, use the process of elimination, narrow
down the culprit or culprits.
In your AUTOEXEC.BAT, CONFIG.SYS, and WIN.INI files you would
eliminate a single command, reboot your system, and test the
application for the problem. If it does not reoccur, you have
PRODUCT : ObjectVision NUMBER : 635
VERSION : 1.0
OS : WIN
DATE : September 11, 1991 PAGE : 4/4
TITLE : Simplifying your Windows system configuration.
found the culprit. Otherwise, eliminate another command, reboot,
try to reproduce the error. Continue this process until the
problem does not reoccur.
Use the same procedure with the OEM drivers. Eliminate each one,
one at a time, testing for the problem in between changes.
Step 8.) If you discover the errors disappear at step five and
can narrow down the application in step seven, check with the
publisher of the offending application for possible workarounds,
or avoid using ObjectVision and this application simultaneously.
Otherwise, contact Borland's ObjectVision Technical Support by
mail, Compuserve, or our Tech. Support Hot-Line (see below). (If
you think you have discovered something that would helpful to us,
we would also greatly appreciate a call.)
Address:
Borland Intel
1800 Green Hills Rd.
Scott's Valley, CA. 95067
Hot-Line number:
(408)439-5300
FAX (408)439-9100
Compuserve:
Forum BORAPP
Section 15, or LIB 15.